Clone conflict

Conflict-aware optimal scheduling of prioritised code clone refactoring

Duplicated or similar source code, also known as code clones, are possible malicious ‘code smells’ that may need to be removed through refactoring to enhance maintainability. Among many potential refactoring opportunities, the choice and order of a set of refactoring activities may have distinguishable effect on the design/code quality measured in terms of software metrics. Moreover, there may ...

To clone or not to clone?

To clone... Or not to clone? That is a good question! Cloning has its advantages, but also its disadvantages. We might not realize what we are doing. It is like a sword with two blades. On one hand, it can save many lives. On the other hand, it can do a lot of harm. A question mark hangs over the future of cloning. Who are we to decide about someone’s life, his future, his happiness?

Clone Removal V/S Clone Avoidance

Cloning occurs in software when there is redundancy in it in form of any similarity. So, the clones need to be removed or it can be avoided from the software in order to mitigate the negative impacts of clones. In this paper we have studied the various factors that affect the decision of avoidance or removal of clones for handling them.

length Clone

Empirical Studies of Clone Mutation and Clone Migration in Clone Genealogies

Duplications and changes made on code segments by developers form code clones. Cloned code segments are exactly the same or have a particular similarity. A set of cloned code segments that have the same similarity with each other become a clone group. A clone genealogy contains several clone groups in different revisions and time periods. Based on different textual similarities, there are three...